-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(atomic): hide unhydrated results #4900
Conversation
7321c6a
to
cffedd0
Compare
Pull Request ReportPR Title✅ Title follows the conventional commit spec. Live demo linksBundle Size
SSR Progress
Detailed logssearch : buildInteractiveResultsearch : buildInteractiveInstantResult search : buildInteractiveRecentResult search : buildInteractiveCitation search : buildGeneratedAnswer recommendation : missing SSR support case-assist : missing SSR support insight : missing SSR support commerce : missing SSR support |
cffedd0
to
e50b0f1
Compare
e50b0f1
to
c2fb466
Compare
This is a corner case, so @lvu285 or @wmannard , I'll ask for your QA validation for this one (this time, and next time when we migrate, then I think it's niche enough that it'll remain fine). Reproduce bug:
Fix showcase:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great fix for now !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @louis-bompart ,
|
c2fb466
to
3543e12
Compare
I think not, I think I was quit accurate with my CSS so shouldbefine:tm: |
https://coveord.atlassian.net/browse/KIT-3775
Inspired by https://bbellmyers.github.io/2020/09/27/fouc-stencil.html.
Not a definitive fix: When Lit migration is done for the atomic-result, we should validate for regression on that front, and also try to improve the behavior even so slightly.
It might also be preferable to migrate all result components first, so that we can "cut" this behavior neatly. (would likely not happen because I think we scan documentFragment from template element, so we should have all the element defined by then (tho maybe not because of race conditions, in which case https://www.abeautifulsite.net/posts/flash-of-undefined-custom-elements might be adapted for our needs)